PR Stack (Queue Instrumentation)

• feat(core): Queue Instrumentation #5249
• feat(core): [Queue Instrumentation 1] Add enableQueueTracing option and messaging span data conventions #5250
• feat(samples): [Queue Instrumentation 2] Add Kafka to Spring Boot 3 sample app #5253
• feat(spring-jakarta): [Queue Instrumentation 3] Add Kafka producer instrumentation #5254
• feat(spring-jakarta): [Queue Instrumentation 4] Add Kafka consumer instrumentation #5255
• feat(spring-boot-jakarta): [Queue Instrumentation 5] Add Kafka queue auto-configuration #5259
• test(samples): [Queue Instrumentation 6] Add Kafka queue system tests #5260
• feat(samples): [Queue Instrumentation 7] Add Kafka to Spring Boot 3 OTel sample apps #5265
• fix(spring-boot-jakarta): [Queue Instrumentation 8] Disable Sentry Kafka spans when OTel is active #5274
• fix(spring-jakarta): [Queue Instrumentation 9] Clean up stale ThreadLocal context in Kafka consumer interceptor #5279
• fix(spring-jakarta): [Queue Instrumentation 10] Fork root scopes and skip when OTel is active in Kafka consumer #5280
• fix(spring-jakarta): [Queue Instrumentation 11] Guard entire span lifecycle in Kafka producer interceptor #5281
• fix(spring-jakarta): [Queue Instrumentation 12] Add Kafka retry count attribute #5282
• fix(spring-jakarta): [Queue Instrumentation 13] Align enqueue time with Python #5283
• ref(kafka): [Queue Instrumentation 14] Extract sentry-kafka module #5288
• feat(samples): [Queue Instrumentation 15] Add opt-in Kafka console e2e coverage #5289
• fix(test): [Queue Instrumentation 16] Enable Kafka profile in system runner #5291
• feat(kafka): [Queue Instrumentation 17] Add manual consumer tracing helper #5312
• ref(samples): [Queue Instrumentation 18] Move Kafka sources into queues.kafka package #5313
• ref(samples): [Queue Instrumentation 19] Drop Kafka auto-config exclude from Spring Boot samples #5314
• ref(kafka): [Queue Instrumentation 20] Log Kafka instrumentation failures #5315
• fix(kafka): [Queue Instrumentation 21] Preserve third-party baggage on Kafka producer records #5316
• test(spring-boot-jakarta): [Queue Instrumentation 22] Cover spring-kafka class-absence gate #5318
• fix(spring-jakarta): [Queue Instrumentation 23] Install Kafka context before trace setup #5319
• fix(kafka): [Queue Instrumentation 24] Read all baggage headers on consumers #5320
• fix(kafka): [Queue Instrumentation 25] Finish producer spans on failures #5321
• fix(kafka): [Queue Instrumentation 26] Mark producer interceptor experimental #5322
• fix(spring-jakarta): [Queue Instrumentation 27] Delegate Kafka record thread-state hooks #5323
• test(samples): [Queue Instrumentation 28] Cover OTel Jakarta Kafka coexistence in CI #5324
• fix(spring-jakarta): [Queue Instrumentation 29] Set body_size on Spring Kafka consumer transaction #5325
• test(spring-jakarta): [Queue Instrumentation 30] Cover Kafka record interceptor lifecycle edge cases #5327
• fix(kafka): [Queue Instrumentation 31] Write enqueued-time header as plain decimal #5328
• test(spring-boot-jakarta): [Queue Instrumentation 32] Filter OTel in Kafka auto-config negative tests #5330
• fix(otel): [Queue Instrumentation 34] Fix OTel messaging span mapping correctness #5337
• fix(kafka): [Queue Instrumentation 35] Inject trace headers without real active span #5338
• fix(kafka): [Queue Instrumentation 36] Avoid dropping customer interceptor #5341
• fix(spring-boot-jakarta): [Queue Instrumentation 37] Skip Kafka autoconfig for OTel agent #5343
• fix(spring-jakarta): [Queue Instrumentation 38] Close leaked Kafka interceptor scope #5345
• fix(test): [Queue Instrumentation 39] Remove stale Kafka container before startup #5347
• feat(spring): [Queue Instrumentation 40] Add Spring Boot 4 Kafka tracing #5348

📜 Description

Avoid installing SentryKafkaRecordInterceptor when the bean post-processor cannot safely read the existing recordInterceptor field from AbstractKafkaListenerContainerFactory.

Before this change, reflection failures fell back to existing = null, and the post-processor still called setRecordInterceptor(sentryInterceptor). That could silently overwrite a customer-configured interceptor.

After this change:

• getExistingInterceptor throws a dedicated exception when reflection fails
• postProcessAfterInitialization logs an error and leaves the bean untouched
• The reflection-failure log now passes the bean name as the format argument and the exception as the throwable
• Existing customer interceptors are still chained as the delegate when reflection succeeds
• Tests cover both the chaining path and the deterministic reflection-failure "do not modify the bean" invariant

💡 Motivation and Context

Addresses review finding R10-F003: reflection fallback silently drops the customer's existing RecordInterceptor.

Customers often use RecordInterceptor for DLQ routing, auditing, or other message handling behavior. If Sentry cannot safely discover the existing interceptor, it must disable consumer tracing for that factory instead of overwriting customer behavior.

💚 How did you test it?

• Ran ./gradlew spotlessApply apiDump
• Ran ./gradlew :sentry-spring-jakarta:test --tests "io.sentry.spring.jakarta.kafka.SentryKafkaConsumerBeanPostProcessorTest"
• Added tests covering customer interceptor chaining and deterministic reflection-failure preservation

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

Continue addressing the remaining Queue Instrumentation review findings.

#skip-changelog

⚠️ Merge this PR using a merge commit (not squash). Only the collection branch is squash-merged into main.